There are many ways that components can define their view files. The usual way is for the component class to directly point to its view file, such as via a static view.file property.

One lesser-used way is to infer the view name based off the component name.

In this example below, the component doesn't explicitly define a view file. So on component registration, Derby looks for a previously registered view named "simple-box".

class SimpleBox {
  static view = {
    is: 'simple-box'
  }
}

That inference isn't working when registering via app.component(SimpleBox), but it does work with the older signature that passes a custom component name in the call, app.component('simple-box', SimpleBox).

This fixes the inference in the first case, where Derby reads the component name off of the class directly.